Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(search-indexer-service): Change prod url #16689

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

RunarVestmann
Copy link
Member

@RunarVestmann RunarVestmann commented Oct 31, 2024

Change prod url

What

  • Due to recent change by devops the prod url could no longer be called, I was told that changing the prod url would be better so here I'm doing just that

Slack discussion: https://islandis.slack.com/archives/C019LNRM6LE/p1730371957246189
https://islandis.slack.com/archives/C04R5PKH8TZ/p1730370825455869

I'll be responsible for changing the webhook url in the cms when the next release goes out

Summary by CodeRabbit

  • New Features

    • Simplified production host URL for the search indexer service, aligning it with development and staging environments.
    • Updated ingress host for improved external access to the search indexer service.
  • Improvements

    • Adjusted health check paths and readiness criteria for better service monitoring.
    • Increased resource limits for the search indexer service to enhance performance.
    • Updated environment variables for improved service communication.
    • Set consistent pod disruption budgets to minimize service disruption during updates.
  • Bug Fixes

    • No bug fixes were made in this release.
  • Documentation

    • No documentation updates were included in this release.

@RunarVestmann RunarVestmann added the automerge Merge this PR as soon as all checks pass label Oct 31, 2024
@RunarVestmann RunarVestmann requested a review from a team as a code owner October 31, 2024 16:44
Copy link
Contributor

coderabbitai bot commented Oct 31, 2024

Walkthrough

The changes in this pull request involve updates to the ingress configuration in both the search-indexer-service.ts file and the values.prod.yaml configuration file. In the search-indexer-service.ts, the production host URL has been simplified by removing the domain suffix. The values.prod.yaml file reflects broader modifications, including updates to ingress hosts, health check paths, resource limits, environment variables, pod disruption budgets, and service account annotations. These changes enhance the configuration's robustness and operational reliability.

Changes

File Path Change Summary
apps/services/search-indexer/infra/search-indexer-service.ts Updated production host URL in ingress configuration from 'search-indexer-service.devland.is' to 'search-indexer-service'.
charts/islandis/values.prod.yaml - Updated ingress host for search-indexer-service from search-indexer-service.devland.is to search-indexer-service.island.is.
- Modified health check readiness path for web service.
- Adjusted resource limits and requests for several services, including increasing memory limit for search-indexer to 4096Mi.
- Updated various environment variables.
- Set maxUnavailable for pod disruption budgets to 1 for several services.
- Annotated service accounts with IAM roles.

Possibly related PRs

Suggested reviewers

  • RunarVestmann
  • thordurhhh

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 33d8462 and 7288e56.

📒 Files selected for processing (1)
  • charts/islandis/values.prod.yaml (1 hunks)
🔇 Additional comments (1)
charts/islandis/values.prod.yaml (1)

1865-1867: LGTM: Production URL update for search-indexer-service

The change to use search-indexer-service.island.is as the ingress host aligns with the production URL standardization.

Let's verify the URL pattern consistency across other services:

✅ Verification successful

URL pattern follows established conventions

Based on the verification results, the URL pattern search-indexer-service.island.is is consistent with other services in the production environment. The results show:

  • Public-facing services use direct .island.is subdomains (e.g., www.island.is, api.island.is)
  • Internal services use the .internal.island.is pattern (e.g., service-portal-api.internal.island.is)
  • The search indexer service follows the public-facing pattern, which is appropriate as it's meant to be accessible by other services
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if other services follow the same URL pattern in production
# Expected: Most internal services should use the .island.is domain

rg -A 1 'host:.*\.island\.is' --no-filename | sort -u

Length of output: 1245


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d0c9471 and 33d8462.

📒 Files selected for processing (1)
  • apps/services/search-indexer/infra/search-indexer-service.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
apps/services/search-indexer/infra/search-indexer-service.ts (2)

Pattern apps/services/**/*: "Confirm that the code adheres to the following:

  • NestJS architecture, including modules, services, and controllers.
  • Dependency injection patterns and service encapsulation.
  • Integration and unit testing coverage and practices."

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
🔇 Additional comments (2)
apps/services/search-indexer/infra/search-indexer-service.ts (2)

Line range hint 119-133: Ensure CMS webhook configuration is updated.

The ingress configuration change looks correct, but as mentioned in the PR objectives, don't forget to:

  1. Update the webhook URL in the CMS during the next release
  2. Coordinate with DevOps team to ensure proper routing is configured

Would you like me to create a GitHub issue to track the CMS webhook update task?


Line range hint 123-133: Confirm security configuration for production environment.

The security configuration looks appropriate:

  • Global auth is explicitly disabled for dev/staging
  • Production maintains stricter security with no auth override

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this PR as soon as all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants